[DOCS-12626] Add OP upgrade guides #32802
Conversation
github-actions
bot
added
Architecture
Preview links (active after the
|
|
|
||
| #### Fixes | ||
|
|
||
| - THe HTTP Client source's authorization strategy has been fixed. |
There was a problem hiding this comment.
Uppercase H in "THe" at the start
| #### New features | ||
|
|
||
| - [OpenTelemetry Collector source][7]: Send logs from your OpenTelemetry Collector to Observability Pipelines. | ||
| - [Datadog CloudPrem destination][8]: Send logs from Observability Pipelines to Datadog CloudPrem. |
There was a problem hiding this comment.
Maybe change up the wording and say "Route logs to Datadog CloudPrem destination"
|
|
||
| #### New features | ||
|
|
||
| - [OpenTelemetry Collector source][7]: Send logs from your OpenTelemetry Collector to Observability Pipelines. |
There was a problem hiding this comment.
Change to "Ingest logs from the OpenTelemetry Collector to Observability Pipelines"
|
|
||
| #### Enhancements | ||
|
|
||
| - The Elasticsearch destination's indexing strategy has been updated to include data streams. |
There was a problem hiding this comment.
Maybe just link to the config page for Elastic dest - https://docs-staging.datadoghq.com/may/op-upgrade-guides/observability_pipelines/destinations/elasticsearch/#set-up-the-destination
|
|
||
| #### New features | ||
|
|
||
| - [The HTTP Client destination][1]: Send logs to an HTTP client, such as a logging platform or SIEM. |
| #### New features | ||
|
|
||
| - [The HTTP Client destination][1]: Send logs to an HTTP client, such as a logging platform or SIEM. | ||
| - [Processor Groups][2]: Organize your processors into logical groups to help you manage them. |
There was a problem hiding this comment.
There was a problem hiding this comment.
It is linked? Are you not seeing it in the preview?
|
|
||
| - [The HTTP Client destination][1]: Send logs to an HTTP client, such as a logging platform or SIEM. | ||
| - [Processor Groups][2]: Organize your processors into logical groups to help you manage them. | ||
| - [Disk][3] and [memory][4] buffering options are available for destinations. |
There was a problem hiding this comment.
There was a problem hiding this comment.
It's linking to the specific Disk and Memory buffering section of that doc. Are you thinking we should just link to the main doc (no anchor links to the sections)?
| - The `decode_lz4` custom function has been updated to support decompressing `lz4` frame data. | ||
| - The Azure Blob Storage and Google Cloud Storage archive destinations' prefix fields support template syntax. | ||
| - The Splunk HEC destination has a custom environment variable. | ||
| - The sample processor has an optional `group_by` parameter. |
There was a problem hiding this comment.
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes